Use Case Scenario:

Barge Priority

When the mode attribute in the <Push> tag is set to barge, the Audio Push Content is accepted as a priority message. However, a barge Audio push is rejected when the telephone is in one of these non-pushable states:

When the telephone is in the process of restoring a retrieved backup file.
When a Local Procedure has been initiated (For more information, see the Avaya one-X Deskphone Edition for 9600 Series IP Telephones Release 1.0 Installation and Maintenance Guide on http://www.avaya.com/support).
When the telephone is already broadcasting received pushed audio content.
When the telephone is already broadcasting transmitted pushed audio content.

In either non-pushable case, the barge audio content, including any notification tones, is discarded and the RTP socket is closed. In all other cases the telephone accepts the barge audio request regardless of any user activity and broadcasts the audio push content through the Speaker.


Use Case Scenario: Q. What happens when a user is on the call and a barge Audio Push Message is sent? A. If a user is on the call and a barge Audio Push Message is sent, the current active call is placed on Hold, and the audio is streamed immediately. If the call is still on Hold when the pushed audio stream ends, the user can select the appropriate Call Appearance button to continue the original call. Note that the far-end party does not get any indication that the current call is being placed on hold.